Vectorized kernels in Parcels#2122
Merged
erikvansebille merged 64 commits intov4-devfrom Aug 19, 2025
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One way to improve performance in Parcels is to 'vectorize' the kernels: i.e. to not make kernels loop over particles, but to have them act on the entire particles. This PR is an implementation of that approach.
The kernel loop has been completely rewritten, and for Parcels users there will be a few important changes
if-statements anymore in their Kernels. Instead, they will need to applynp.where()or masked indexing. But note that even complex Kernels like RK45 with adaptive times-tapping are still possibleparticlebut a set ofparticlesand b)timedoes not have much meaning anymore when all particles could potentially have their own time. See also Reconsider Kernel signature for Parcels v4 #2147Nparticles, the memory requirements of temporary variables is now much more likely to grow quickly.The performance of this PR has been explored in Parcels-code/parcels-benchmarks#2 (comment)
mainfor v3 changes,v4-devfor v4 changes)